• picking up a given file from the local file system and
• detaching a received file in the JMS payload to the local file system

• Enable logging to console window by editing the following line in <XPDINTEG_HOME>/rcp/eclipse/features/com.ibm.rcp.integrator.feature_<version>.<build>/handler.properties

-Dcom.ibm.rcp.integrator.showflowstatus=true 

Figure 4: Expeditor integrator runtime console (OSGi Console)

• Locate the XPDinteg.xml file under <XPDINTEG_HOME>/config
• Copy the file to the new directory (<XPDINTEG_HOME>/config/new)
• Depending on the configured polling interval for the Configuration Update Resource Adapter, the new configuration file will be discovered and applied (standard value = 60’000 msec = 1 min)
• The new configuration file is automatically processed and applied. The Expeditor integrator console will show a log message which confirms the configuration change (see console output in Figure 5)

Figure 5: Expeditor integrator console output during manual configuration update

• On appearance, transfer given file from given directory to messaging back-end
• Transfer file from messaging back-end to Expeditor integrator and detach it to given local directory

1. Set-up the required standard back-end queues as described in chapter ‎2 Queue Configuration at Application Integration Back-end .
2. Edit the XPDinteg.xml file (previously provided as Sample_for_LocalFSTransfers_XPDinteg.xml) and configure the back-end messaging connection (Messaging Service):
• Provide the unique LocationId (place holder = location_id)
• Configure the Messaging Service by replacing the included place holders with your values (more details are given in chapter ‎4.3.3 Configuration of Back-end Connectivity through Lotus Expeditor micro broker bridge). Replace:
• backbone_service_bus,
• backbone_svc_bus_port,
• MQ_backend_Q_manager,
• MQ_backend_srv_channel
• Replace back-end queue names in remote queue configuration section of XPDinteg.xml with your back-end queue names configured in Step 1 above (e.g. replace ReqOutQx, ResInQx and CtrlOutQx in section 4.1 of XPDinteg.xml with your environment settings).

• checkadapterstatus <adapter_name>
• checkmsgserverstatus <pipe_name>

1. Configure Expeditor integrator to transfer the given XPDinteg_sample.txt file from the <XPDINTEG_HOME>/datatrans/outbound directory to the back-end messaging system:
• Open the XPDinteg.xml file and note the Local File System Resource Adapter configuration for monitoring the <XPDINTEG_HOME>/datatrans/outbound directory for existence of the XPDinteg_sample.txt file (poll every minute). Review the provided configuration under <resource-monitor-service> (see Listing 1).
  Note, that the ResourceType=SampleFileSystemFile is assigned to this adapter. This will be used to further configure the file transfer options under the Resource Mapper (see Listing 1).
• Furthermore, locate the Resource Mapper configuration in the @nowiki@13section of the XPDinteg.xml and review the configuration for the ResourceType=SampleFileSystemFile (Listing 2).
  Note, that the original XPDinteg_sample.txt file will be copied to XPDinteg_sample-transferred.txt when it was successfully transferred to the back-end system.
  
  Listing 1: File System Adapter configuration example for SampleFileSystemFile
  

  <resource-monitor-service>
  

    <adapters>
  

      <adapter type="XPDINTEG_FILE_SYSTEM_ADAPTER" name="AdapterForLocalFile">
  

        <polling>
  

          <interval>60000</interval>
  

          <meta-data>ASCII-datatrans/outbound/XPDinteg_sample.txt</meta-data>
  

          <topic>com/ibm/integrator/flowtriggerevent/FileTransfer/LocalFileSystem/LocalFileSystemAdapter
  

          </topic>
  

        </polling>
  

        <configuration>
  

          <param name="ResourceType" value="SampleFileSystemFile"/>
  

        </configuration>
  

  </adapter>

  
  
  Listing 2: Resource Mapper configuration example (outbound: Expeditor integrator -> back-end). When file is picked up, the source file XPDinteg_sample.txt is copied to XPDinteg_sample-transferred.txt in the source directory /datatrans/outbound/)
  

  <resources>
  

  <outbound-mappings>			
  

  	<resource-mapping type="SampleFileSystemFile">
  

  		<param name="TransportType" value="LocalFileSystem"/>
  

  		<param name="Description" value="Sample mapper for local files in datatrans outbound dir"/>
  

  		<param name="TransferMode" value="ASCII"/>
  

  		<param name="TransferConfirmationMode" value="WriteOtherFile"/>
  

  		<param name="WriteOtherFileName" value="datatrans/outbound/XPDinteg_sample-transferred.txt"/>
  

  		<param name="Encoding" value="UTF-8"/>
  

  		<param name="TransferPriority" value="9"/>
  

  	</resource-mapping>
  

  
  
2. Configure Expeditor integrator to detach the payload of a received message with the following JMS Custom Header values:
   
   MessagePurpose=FileTransfer
   TransportType=LocalFileSystem
   ResourceType=SampleFileSystemFile
   LocationId=your_id, MessageId=your_msg_id, TransactionId=your_trans_id, EoD=true
   
   to the <XPDINTEG_HOME>datatrans/inbound directory as sample.txt file.
   
• Create a message which contains a sample ASCII file with the required JMS Custom Header values above .
• Locate the Resource Mapper configuration in the <resources><inbound-mappings> section of the XPDinteg.xml and review the configuration for the ResourceType=SampleFileSystemFile (see Listing 3).
  Note, that the received message payload will be detached as sample.txt file into the <XPDINTEG_HOME>/datatrans/inbound directory.
  
  Listing 3: Resource Mapper configuration example (inbound: Payload of received FileTransfer message with ResourceType=SampleFileSystemFile is detached as sample.txt file to local datatrans/inbound directory)
  

  <resources>
  

    <inbound-mappings>
  

  	<resource-mapping type="SampleFileSystemFile">
  

  	<!-- Kicks of Sample_PutSampleLocalFileSystemFile.flow -->			 
  

  		<param name="TransportType" value="LocalFileSystem"/>
  

  		<param name="Description" value="Write sample file system file to datatrans inbound directory"/>
  

  		<param name="TransferMode" value="ASCII"/>
  

  		<param name="DestinationCreationMode" value="APPEND"/>
  

  		<param name="DestinationPath" value="datatrans/inbound"/>
  

  		<param name="DestinationName" value="sample.txt"/>
  

  		<param name="Encoding" value="UTF-8"/>
  

  	</resource-mapping>
  

  
  
3. Apply the changed configuration to the Expeditor integrator runtime:
• If Expeditor integrator is running, please, stop it (Type close into the console window and press Enter.)
• Re-name <XPDINTEG_HOME>/datatrans/outbound/sample.txt in XPDinteg_sample.txt
• Run <XPDINTEG_HOME>/resetscript/XPDintegReset.bat
• Start Expeditor integrator by running <XPDINTEG_HOME>/XPDintegStart.bat
• Now, wait until the /datatrans/outbound/XPDinteg_sample.txt file is picked up (the XPDinteg_sample-transferred.txt copy will appear).
• Send the FileTransfer message from Step_2 with ResourceType=SampleFileSystemFile to the Expeditor integrator and notice that the message payload is detached as sample.txt file to the datatrans/inbound directory.

2008-11-25 13:59:18.686 : GetFileSystemFiles_Process/STARTED

2008-11-25 13:59:19.092 : GetFileSystemFiles_Process/FINISHED